home *** CD-ROM | disk | FTP | other *** search
- ****************************************
- The Video Librarian: A Short User Guide
- ----------------------------------------
-
- DESCRIPTION
- -----------
-
- VIDLIB is a public domain program for storing information about
- video cassettes. The information stored for each tape is:
-
- CATEGORY: A user-defined classification, such
- as ADULT, MUSICAL, FOREIGN, etc.
-
- LOCATION: A text field for where the tape
- is kept, such as CLOSET, VIDEO
- CABINETTE, ON LOAN, SLOT 22, etc.
-
- TITLES: There are two title fields for
- each tape.
-
- NOTES: A text field for any other
- information you wish to keep.
-
- TIME: A field for storing the
- amount of time remaining on
- a tape.
-
- These fields are all optional (there are no required fields).
- They are also free-form, meaning that they will accept any
- value in any format. Text is converted to upper case.
-
- MENUS
- -----
-
- VIDLIB uses a bounce-bar menu system. To select an option,
- use the UP and Down arrow keys to highlight your choice
- and press the Enter (or Carraige Return) key.
-
- SAMPLE DATA FILE
- ----------------
-
- The VIDLIB archive file contains a sample data file to
- help get you started. To access this file, select the
- menu option, "Load an EXISTING data file". At the
- file name prompt, enter the word SAMPLE. When the ACTION
- MENU appears, select the option, "VIEW, MODIFY, or
- DELETE Tapes". Then use the arrow keys to scroll
- through the data base.
-
- FILE EXTENSIONS
- ---------------
-
- When creating a NEW data file, VIDLIB appends the extension
- of DAT. When loading an EXISTING data file, VIDLIB saves the
- previous version with the extension of BAK. When transferring
- your data to an ASCII file, VIDLIB uses an extension of TXT.
- Existing files with these names will be overlaid.
-
- COMBINING FILES
- ---------------
-
- Two data files can be merged together with the /b option,
- for example:
-
- copy /b sample.dat + myfile.dat
-
-
-
- UPDATING AND MISC TIPS
- ----------------------
-
- Just like LOTUS, user interaction in VIDLIB
- occurs entirely in memory. You are advised
- that lengthy periods of data entry should be
- punctuated by SAVES.
-
- A mistake, such as an accidental deletion can
- be reversed in two ways:
-
- 1. Do not save your changes.
- 2. Copying the backup file
- into the data file.
-
- Take backups.
-
-
- MEMORY REQUIREMENTS
- -------------------
-
- A 256K machine with no resident software can support a data
- base containing about 1,000 video tapes. As memory size
- increases, the size of the data base can increase
- correspondinly. Of course, you can also use multiple
- data files to circumvent any memory constraints.
-
- PRINTING
- --------
-
- To obtain a "hard-copy" of your tapes, select the OUTBOUND
- INTERFACES option from the ACTION MENU. The printer function
- terminates with an HP LaserJet control sequence for a page
- eject.
-
- MISC
- ----
-
- VIDLIB was first uploaded to CIS - go ibmsw, on 12/14/87.
- You can contact me through CIS: 72307, 3311. I am especially
- interested in hearing from anyone who taped any of these:
-
- * The Ring of the Nibelungen series (broadcast on
- PBS in 1981 before I had a VCR)
-
- * The Brideshead Revisited series (which I
- accidentally erased to the eternal
- chagrin of my wife)
-
-
- FILE LAYOUT, INTERNALS, AND OTHER GIBBERISH
- -------------------------------------------
-
- The following code fragment provides the internal
- record layout used by VIDLIB.
-
- typedef struct
- {
- qint hash_key;
- qstring05 signature;
- qstring20 category;
- qstring40 title[2];
- qstring20 location;
- qstring40 notes[1];
- qstring05 times;
- } tape_record;
-
- VIDLIB uses a forward linked list data structure
- which is sorted by concatenating the category and title
- elements.
-
- Printing is done through service 0 of interrupt 17h and
- directed to LPT1. The function for doing this is...
-
- unsigned int chr_to_lpt1
- (
- unsigned int chr
- )
- {
- asm mov ax, chr
- asm mov ah, 0
- asm mov dx, 0
- asm int 17h
- asm mov al, ah
- asm and ax, 1
- }
-
- The program itself is written in TURBO C, using the large
- memory model.
-
-
-